Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42b2eda4e6490c1035eecb94a1f3f3f25cb0e445b2072f74c07de28e05d2c201

Tx prefix hash: 437f8dc45e243d5ad60643381206efc0ca76d55bc795ce3ccb7b2d1637ccb191
Tx public key: aeaab33fe4441de996d6ded580f882da43e57989e54e544adbfa3bdd77f6e3eb
Timestamp: 1655818001 Timestamp [UCT]: 2022-06-21 13:26:41 Age [y:d:h:m:s]: 02:216:02:32:59
Block: 527232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 675718 RingCT/type: yes/0
Extra: 01aeaab33fe4441de996d6ded580f882da43e57989e54e544adbfa3bdd77f6e3eb02110000000775e3f0e9000000000000000000

1 output(s) for total of 10.991619483000 dcy

stealth address amount amount idx
00: 6d79323c46790c5e8dcea45d58cbb9b60a335c2274846812dcfd4326e472c9b3 10.991619483000 955885 of 0

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": 527242, "vin": [ { "gen": { "height": 527232 } } ], "vout": [ { "amount": 10991619483, "target": { "key": "6d79323c46790c5e8dcea45d58cbb9b60a335c2274846812dcfd4326e472c9b3" } } ], "extra": [ 1, 174, 170, 179, 63, 228, 68, 29, 233, 150, 214, 222, 213, 128, 248, 130, 218, 67, 229, 121, 137, 229, 78, 84, 74, 219, 250, 59, 221, 119, 246, 227, 235, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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