Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a05d3436569b11c5da39385fe28df11f8933f4c00969307450f6795d767d2cb

Tx prefix hash: 610eb3b346fcb78a379909260072b14ae1e857ebf86a9101eea9923a61e23cd2
Tx public key: acda2ea1edc57147c992a6e2ba3c9bc3134e37e751e803a212fcdbdf9a8896f9
Timestamp: 1731864989 Timestamp [UCT]: 2024-11-17 17:36:29 Age [y:d:h:m:s]: 00:131:06:42:32
Block: 1155832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93644 RingCT/type: yes/0
Extra: 01acda2ea1edc57147c992a6e2ba3c9bc3134e37e751e803a212fcdbdf9a8896f9021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 676700c0762465b9719208546707f0a38cbf30076eb61a0b7c79db46a6ac51ac 0.600000000000 1641451 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": 1155842, "vin": [ { "gen": { "height": 1155832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "676700c0762465b9719208546707f0a38cbf30076eb61a0b7c79db46a6ac51ac" } } ], "extra": [ 1, 172, 218, 46, 161, 237, 197, 113, 71, 201, 146, 166, 226, 186, 60, 155, 195, 19, 78, 55, 231, 81, 232, 3, 162, 18, 252, 219, 223, 154, 136, 150, 249, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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