Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0dee15bf71082b945d02d36fca3aa0b426d6db156915e9df3487cce479f55ca6

Tx prefix hash: bb63dd5eb774144d9f1970d5525dacb0831555e6ebb5bcf1138960b4d1a37d4d
Tx public key: 85ba745673926d04fc4487d121d183c6d5f992a7703000f5e3ea8a85cff0e8e4
Timestamp: 1736821472 Timestamp [UCT]: 2025-01-14 02:24:32 Age [y:d:h:m:s]: 00:154:16:44:49
Block: 1196871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110276 RingCT/type: yes/0
Extra: 0185ba745673926d04fc4487d121d183c6d5f992a7703000f5e3ea8a85cff0e8e4021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 008bd0e7bf107157948b85927404a3215a928d0b6a89ce8a7532e19216cbafc2 0.600000000000 1683474 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1196881, "vin": [ { "gen": { "height": 1196871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "008bd0e7bf107157948b85927404a3215a928d0b6a89ce8a7532e19216cbafc2" } } ], "extra": [ 1, 133, 186, 116, 86, 115, 146, 109, 4, 252, 68, 135, 209, 33, 209, 131, 198, 213, 249, 146, 167, 112, 48, 0, 245, 227, 234, 138, 133, 207, 240, 232, 228, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8