Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93dd7c56027b832fc24afed377c6d4e9133aa71a1b97a7aec376cf5db9278d10

Tx prefix hash: 2d64977472a29e20d06869beec19d6634f97df2996ae8e45a0d4ff7bdf9ec108
Tx public key: f88e8294b689d6ae6010700b5559e43db1fd959c8508dc0d1a9cd490c763f5e0
Timestamp: 1580269718 Timestamp [UCT]: 2020-01-29 03:48:38 Age [y:d:h:m:s]: 05:012:13:57:18
Block: 54862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160093 RingCT/type: yes/0
Extra: 01f88e8294b689d6ae6010700b5559e43db1fd959c8508dc0d1a9cd490c763f5e002110000003d4ac5aa02000000000000000000

1 output(s) for total of 403.850147242000 dcy

stealth address amount amount idx
00: e2ad4ea94564a3af163ae9cbd4ead2d5e58fa0e13f3e168a6760d6f07a3e2f73 403.850147242000 101380 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": 54872, "vin": [ { "gen": { "height": 54862 } } ], "vout": [ { "amount": 403850147242, "target": { "key": "e2ad4ea94564a3af163ae9cbd4ead2d5e58fa0e13f3e168a6760d6f07a3e2f73" } } ], "extra": [ 1, 248, 142, 130, 148, 182, 137, 214, 174, 96, 16, 112, 11, 85, 89, 228, 61, 177, 253, 149, 156, 133, 8, 220, 13, 26, 156, 212, 144, 199, 99, 245, 224, 2, 17, 0, 0, 0, 61, 74, 197, 170, 2, 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