Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 488d69c868c1069dec9933462d3acb6c91a53c2c9b6c71381b34ee5e650cbb51

Tx prefix hash: e115635d70144535e2f5301a89f5d5b683dca1ab0c431be4fd6acfff09dcea36
Tx public key: b0ef6ba8375b093211880ec23f6a1107bf9ee309dbdcb5a6f56492c03fa15f3f
Timestamp: 1736634610 Timestamp [UCT]: 2025-01-11 22:30:10 Age [y:d:h:m:s]: 00:157:21:55:19
Block: 1195313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112571 RingCT/type: yes/0
Extra: 01b0ef6ba8375b093211880ec23f6a1107bf9ee309dbdcb5a6f56492c03fa15f3f0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68a3dcb0242ba17e681e23cbf5722c5c9bce8235a7a83b46c66625cd20861269 0.600000000000 1681902 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": 1195323, "vin": [ { "gen": { "height": 1195313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68a3dcb0242ba17e681e23cbf5722c5c9bce8235a7a83b46c66625cd20861269" } } ], "extra": [ 1, 176, 239, 107, 168, 55, 91, 9, 50, 17, 136, 14, 194, 63, 106, 17, 7, 191, 158, 227, 9, 219, 220, 181, 166, 245, 100, 146, 192, 63, 161, 95, 63, 2, 17, 0, 0, 0, 6, 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