Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 451b479916f60e85d071094e615269c865da2e08f1481b7d8edd835163140f98

Tx prefix hash: e918e66bb8c933cfe36c405d9af8b87dde956485bfb1c12316a6a5b498c07dd6
Tx public key: 4cb405c4b09bf9860d12524c283874a54069ca9f96bad70d69b1a58fb455491e
Timestamp: 1715646611 Timestamp [UCT]: 2024-05-14 00:30:11 Age [y:d:h:m:s]: 00:325:23:09:12
Block: 1021456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232998 RingCT/type: yes/0
Extra: 014cb405c4b09bf9860d12524c283874a54069ca9f96bad70d69b1a58fb455491e0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e68fa490551e7ced3e9d2d692a5e870673b65a99bcbcc8a9d7175c694d7a962 0.600000000000 1485781 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": 1021466, "vin": [ { "gen": { "height": 1021456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e68fa490551e7ced3e9d2d692a5e870673b65a99bcbcc8a9d7175c694d7a962" } } ], "extra": [ 1, 76, 180, 5, 196, 176, 155, 249, 134, 13, 18, 82, 76, 40, 56, 116, 165, 64, 105, 202, 159, 150, 186, 215, 13, 105, 177, 165, 143, 180, 85, 73, 30, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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