Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5926f993554b7f889b41b47dcdf521d45486439c13b747b8afa0f955a9f9ff75

Tx prefix hash: 5432747b7959ddb281677372c6de116eb761f7d4a10e251ed4b716aad1ab73d9
Tx public key: 6a0757e04be55cfbf7cb4093254765df218b7b5dea2a973d6e12c963c5990418
Timestamp: 1713828326 Timestamp [UCT]: 2024-04-22 23:25:26 Age [y:d:h:m:s]: 00:308:05:37:46
Block: 1006384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220327 RingCT/type: yes/0
Extra: 016a0757e04be55cfbf7cb4093254765df218b7b5dea2a973d6e12c963c599041802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbd092504e08bee93744067bde40e54611bc60e3ba14b0b41ee41179f6c5cca5 0.600000000000 1467406 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": 1006394, "vin": [ { "gen": { "height": 1006384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbd092504e08bee93744067bde40e54611bc60e3ba14b0b41ee41179f6c5cca5" } } ], "extra": [ 1, 106, 7, 87, 224, 75, 229, 92, 251, 247, 203, 64, 147, 37, 71, 101, 223, 33, 139, 123, 93, 234, 42, 151, 61, 110, 18, 201, 99, 197, 153, 4, 24, 2, 17, 0, 0, 0, 2, 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