Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76ce3170a5bd3fc1dcb3fdb604fa07ac8b23200590ea52d7d966c2de6db5b76a

Tx prefix hash: 96173187d3a44ddf2f05bce4068d6f7afc895402c4bcb2cfa81dda51f7c47a57
Tx public key: 84733ff5f98c3c44078de6e1916b6c09bbe23de4abfb53109ad332ad8a03f6ad
Timestamp: 1712835788 Timestamp [UCT]: 2024-04-11 11:43:08 Age [y:d:h:m:s]: 00:202:19:41:21
Block: 998127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145239 RingCT/type: yes/0
Extra: 0184733ff5f98c3c44078de6e1916b6c09bbe23de4abfb53109ad332ad8a03f6ad0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b88e02ec85cea10c6abf7619e4f342f56f74e27c0a78630b271f09e2da0b699e 0.600000000000 1458569 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": 998137, "vin": [ { "gen": { "height": 998127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b88e02ec85cea10c6abf7619e4f342f56f74e27c0a78630b271f09e2da0b699e" } } ], "extra": [ 1, 132, 115, 63, 245, 249, 140, 60, 68, 7, 141, 230, 225, 145, 107, 108, 9, 187, 226, 61, 228, 171, 251, 83, 16, 154, 211, 50, 173, 138, 3, 246, 173, 2, 17, 0, 0, 0, 4, 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