Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33f17c79c0ec632ebfea4df9e41f54c671abee3aafea2f58af89fc7edd960d08

Tx prefix hash: cfb19459b904cfe2e162e1211dd471bdf93fb50e04ad290ff1a5c7fa82a0083c
Tx public key: b1441e4ff19767a8044494b95f13c16b29b555cc96d3b47c3b95fce923c7cc07
Timestamp: 1710670334 Timestamp [UCT]: 2024-03-17 10:12:14 Age [y:d:h:m:s]: 00:187:19:43:53
Block: 980224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134520 RingCT/type: yes/0
Extra: 01b1441e4ff19767a8044494b95f13c16b29b555cc96d3b47c3b95fce923c7cc070211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d7a5a9b83c711ef43c6c701ea85952e873bfe30bc5e7451fbdd10989e404615 0.600000000000 1440289 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": 980234, "vin": [ { "gen": { "height": 980224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d7a5a9b83c711ef43c6c701ea85952e873bfe30bc5e7451fbdd10989e404615" } } ], "extra": [ 1, 177, 68, 30, 79, 241, 151, 103, 168, 4, 68, 148, 185, 95, 19, 193, 107, 41, 181, 85, 204, 150, 211, 180, 124, 59, 149, 252, 233, 35, 199, 204, 7, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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