Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac52feb1c5dfc144902519b85428b1a013139887c093a671963436b698569822

Tx prefix hash: b58c697d4c32e8843dcf55c83bcf87dd94daaf15682fc11210e85a6faeec5942
Tx public key: 51b3ceb7be9c29c64753d293f6ccb1a71bda2a3b0f1a99ef2c4c359e650c9f92
Timestamp: 1719860184 Timestamp [UCT]: 2024-07-01 18:56:24 Age [y:d:h:m:s]: 00:256:19:58:59
Block: 1056393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183523 RingCT/type: yes/0
Extra: 0151b3ceb7be9c29c64753d293f6ccb1a71bda2a3b0f1a99ef2c4c359e650c9f92021100000006ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 839e427fd206e3dc41e742488f3164a26c89e6567b0ba2ca0cdb464800f7e180 0.600000000000 1526806 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": 1056403, "vin": [ { "gen": { "height": 1056393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "839e427fd206e3dc41e742488f3164a26c89e6567b0ba2ca0cdb464800f7e180" } } ], "extra": [ 1, 81, 179, 206, 183, 190, 156, 41, 198, 71, 83, 210, 147, 246, 204, 177, 167, 27, 218, 42, 59, 15, 26, 153, 239, 44, 76, 53, 158, 101, 12, 159, 146, 2, 17, 0, 0, 0, 6, 221, 211, 219, 145, 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