Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a91dd84b348b145962aaee7d58b56258740b40c743614eb640a0dfcfada1c3a

Tx prefix hash: d0293daa43eb164d2d8727216db0ea6e31ee9824426e5e4b55c24c6f209de8ed
Tx public key: a9a3fb2154570b26489af70c7d87aca429a8de61e52d9d07a1c878de6e2c0542
Timestamp: 1737150922 Timestamp [UCT]: 2025-01-17 21:55:22 Age [y:d:h:m:s]: 00:151:14:35:50
Block: 1199597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108060 RingCT/type: yes/0
Extra: 01a9a3fb2154570b26489af70c7d87aca429a8de61e52d9d07a1c878de6e2c05420211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08bfcbb644e1f935678fed9ea74fd43b2627bead776b04b950087d0ddcc9fc20 0.600000000000 1686230 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": 1199607, "vin": [ { "gen": { "height": 1199597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08bfcbb644e1f935678fed9ea74fd43b2627bead776b04b950087d0ddcc9fc20" } } ], "extra": [ 1, 169, 163, 251, 33, 84, 87, 11, 38, 72, 154, 247, 12, 125, 135, 172, 164, 41, 168, 222, 97, 229, 45, 157, 7, 161, 200, 120, 222, 110, 44, 5, 66, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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