Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a07fa5ced0071192c5358a25d9e4839454dd0aa698a155bc765b89fb5beea0a

Tx prefix hash: 3081c1174d360cc3cf4351cb0003503668d72f3a4f72f393b962136dcb094a4e
Tx public key: d70738f4c1ebf7800fe9cb80f2d060050881000a1509b8009fb99c11e242d567
Timestamp: 1718557407 Timestamp [UCT]: 2024-06-16 17:03:27 Age [y:d:h:m:s]: 00:333:08:04:50
Block: 1045618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238206 RingCT/type: yes/0
Extra: 01d70738f4c1ebf7800fe9cb80f2d060050881000a1509b8009fb99c11e242d56702110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e01b8a25a9fdaa3a00a621cfd5e3477fab8696901d56a328cb98e76d50a9ebe3 0.600000000000 1515237 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": 1045628, "vin": [ { "gen": { "height": 1045618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e01b8a25a9fdaa3a00a621cfd5e3477fab8696901d56a328cb98e76d50a9ebe3" } } ], "extra": [ 1, 215, 7, 56, 244, 193, 235, 247, 128, 15, 233, 203, 128, 242, 208, 96, 5, 8, 129, 0, 10, 21, 9, 184, 0, 159, 185, 156, 17, 226, 66, 213, 103, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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