Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de5b8754827bbb1a1ef0c32aa581d168fb68cc9582aa4ee57f8b44af7cea75f0

Tx prefix hash: 8b0018c511a82726756c0e47947e22185ac34adfee3cec5df36040f250548395
Tx public key: 9c17eb26749bbfd9812cbb2a0cf2ae6c7c7b4281691551d6b9fb123f66ccb22e
Timestamp: 1707232179 Timestamp [UCT]: 2024-02-06 15:09:39 Age [y:d:h:m:s]: 00:298:19:52:34
Block: 951692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213968 RingCT/type: yes/0
Extra: 019c17eb26749bbfd9812cbb2a0cf2ae6c7c7b4281691551d6b9fb123f66ccb22e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fcfd0ece1f5947222625a08f37ae9301d60ee044be5642b063bb2d3816d0f1b 0.600000000000 1410496 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": 951702, "vin": [ { "gen": { "height": 951692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fcfd0ece1f5947222625a08f37ae9301d60ee044be5642b063bb2d3816d0f1b" } } ], "extra": [ 1, 156, 23, 235, 38, 116, 155, 191, 217, 129, 44, 187, 42, 12, 242, 174, 108, 124, 123, 66, 129, 105, 21, 81, 214, 185, 251, 18, 63, 102, 204, 178, 46, 2, 17, 0, 0, 0, 1, 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