Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66acd7d1e09eefd0948b378a2360425460e25af8ca0d78c775d5caac30711115

Tx prefix hash: 69cf6a9312441017b380db72a376f6c86755e20c3df7dbcc8f321a8d904d934d
Tx public key: f954aa4fdf251f600c1bcdaebba2fd48799d9507e603b1c4ff83cf574c3f6914
Timestamp: 1729038590 Timestamp [UCT]: 2024-10-16 00:29:50 Age [y:d:h:m:s]: 00:098:04:36:48
Block: 1132509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70120 RingCT/type: yes/0
Extra: 01f954aa4fdf251f600c1bcdaebba2fd48799d9507e603b1c4ff83cf574c3f6914021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 319465b3a4a23b6036f88663b6e36876acb1ed56437255b1bd1291436bf3e48e 0.600000000000 1615434 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": 1132519, "vin": [ { "gen": { "height": 1132509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "319465b3a4a23b6036f88663b6e36876acb1ed56437255b1bd1291436bf3e48e" } } ], "extra": [ 1, 249, 84, 170, 79, 223, 37, 31, 96, 12, 27, 205, 174, 187, 162, 253, 72, 121, 157, 149, 7, 230, 3, 177, 196, 255, 131, 207, 87, 76, 63, 105, 20, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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