Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc3c11999ecde71448fc2399188fff8086d08f5decc51b6beb39e73f1860d64c

Tx prefix hash: af52d206912864ab94f5317d9a0d789ef2e2c6998d9465dc3e1d6a2d64e8dd7a
Tx public key: b75f887fdba2e3a127f554e9dede75b753d5a06724cb3434c9c7fb99f0a7d72d
Timestamp: 1717013750 Timestamp [UCT]: 2024-05-29 20:15:50 Age [y:d:h:m:s]: 01:165:15:04:58
Block: 1032804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376960 RingCT/type: yes/0
Extra: 01b75f887fdba2e3a127f554e9dede75b753d5a06724cb3434c9c7fb99f0a7d72d02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 655729d3ea9e4a4aa510a66c6c8b3bb9a5fd87f491c78d4e7d0733809dafb3bd 0.600000000000 1501259 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": 1032814, "vin": [ { "gen": { "height": 1032804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "655729d3ea9e4a4aa510a66c6c8b3bb9a5fd87f491c78d4e7d0733809dafb3bd" } } ], "extra": [ 1, 183, 95, 136, 127, 219, 162, 227, 161, 39, 245, 84, 233, 222, 222, 117, 183, 83, 213, 160, 103, 36, 203, 52, 52, 201, 199, 251, 153, 240, 167, 215, 45, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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