Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c50cc6fb109ca4bcd7ff3371b167df148601ed994a2741ba3f705ecc3af1986a

Tx prefix hash: 3df8a7caee5684d0f7e9ee06c3fde2be156470784f0b1022d65fcd037f596d56
Tx public key: 5bb4440491e3f4239dd9dbfaafbae8aa781c8bce567d0f700154c7f921c55b8e
Timestamp: 1746677837 Timestamp [UCT]: 2025-05-08 04:17:17 Age [y:d:h:m:s]: 00:196:15:06:10
Block: 1278195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138246 RingCT/type: yes/0
Extra: 015bb4440491e3f4239dd9dbfaafbae8aa781c8bce567d0f700154c7f921c55b8e0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 652cee5f5cdae59e671ee97b48c07e9d429bbf7abae38846d0cb31638e6ad64f 0.600000000000 1765560 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": 1278205, "vin": [ { "gen": { "height": 1278195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "652cee5f5cdae59e671ee97b48c07e9d429bbf7abae38846d0cb31638e6ad64f" } } ], "extra": [ 1, 91, 180, 68, 4, 145, 227, 244, 35, 157, 217, 219, 250, 175, 186, 232, 170, 120, 28, 139, 206, 86, 125, 15, 112, 1, 84, 199, 249, 33, 197, 91, 142, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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