Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05f71351332cfe3bc8264b037ecc6a4b0380a8eb75076ff8f636422dcd0f2c4b

Tx prefix hash: 39ddce6e784a66284c0bd31b7d416d8a063ab1eede383d3ce14c0b33b49edbd7
Tx public key: 259e050fcf04bb744efc269eed475e0ce66a6f568325917eaf38c8b64e7fdd2c
Timestamp: 1715381302 Timestamp [UCT]: 2024-05-10 22:48:22 Age [y:d:h:m:s]: 00:232:19:38:18
Block: 1019279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166614 RingCT/type: yes/0
Extra: 01259e050fcf04bb744efc269eed475e0ce66a6f568325917eaf38c8b64e7fdd2c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d5c1ccfb0471dd2b31d572a8011fb4d8c73ffb9073b38adb6ee4dccd87e3801 0.600000000000 1483204 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": 1019289, "vin": [ { "gen": { "height": 1019279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d5c1ccfb0471dd2b31d572a8011fb4d8c73ffb9073b38adb6ee4dccd87e3801" } } ], "extra": [ 1, 37, 158, 5, 15, 207, 4, 187, 116, 78, 252, 38, 158, 237, 71, 94, 12, 230, 106, 111, 86, 131, 37, 145, 126, 175, 56, 200, 182, 78, 127, 221, 44, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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