Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a457d2ccac352b34e360925cfaa7bf2e93f11ebd329fc6c6de0d28e9efb9469

Tx prefix hash: 09f58805f82743658565dffdbc023e3b80adddaa3413422747367e75efa6591a
Tx public key: fd6a1363192248729af8fcea0ee1b92c1b9980ad3de353b7410b227633f4416c
Timestamp: 1730492904 Timestamp [UCT]: 2024-11-01 20:28:24 Age [y:d:h:m:s]: 00:080:11:13:34
Block: 1144459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57534 RingCT/type: yes/0
Extra: 01fd6a1363192248729af8fcea0ee1b92c1b9980ad3de353b7410b227633f4416c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5ce2a0b14eea1fc0f29426d6f4249c7da41f00fdad42560d8c7f1b1646b1d4c 0.600000000000 1628682 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": 1144469, "vin": [ { "gen": { "height": 1144459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5ce2a0b14eea1fc0f29426d6f4249c7da41f00fdad42560d8c7f1b1646b1d4c" } } ], "extra": [ 1, 253, 106, 19, 99, 25, 34, 72, 114, 154, 248, 252, 234, 14, 225, 185, 44, 27, 153, 128, 173, 61, 227, 83, 183, 65, 11, 34, 118, 51, 244, 65, 108, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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