Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baddf3d64d76da3b28fa1e04d0846cfcbe72738a943f567f95cf64c909db95cb

Tx prefix hash: 021d8eb3ab79a6effdda1d190a67a3876ad290cd78fc7d8b7161cecc68f142a6
Tx public key: d2ce4a5dd369b2d9bb6fd93ea2b9c5e0fc8b35cecd1472ed016c444e22212148
Timestamp: 1726516877 Timestamp [UCT]: 2024-09-16 20:01:17 Age [y:d:h:m:s]: 00:208:05:00:17
Block: 1111580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148636 RingCT/type: yes/0
Extra: 01d2ce4a5dd369b2d9bb6fd93ea2b9c5e0fc8b35cecd1472ed016c444e2221214802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4da2c0d3c26977a1d1b5ad6afe7b3695e2129149708f23e7d4ed764caf758316 0.600000000000 1590593 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": 1111590, "vin": [ { "gen": { "height": 1111580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4da2c0d3c26977a1d1b5ad6afe7b3695e2129149708f23e7d4ed764caf758316" } } ], "extra": [ 1, 210, 206, 74, 93, 211, 105, 178, 217, 187, 111, 217, 62, 162, 185, 197, 224, 252, 139, 53, 206, 205, 20, 114, 237, 1, 108, 68, 78, 34, 33, 33, 72, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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