Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aba5f31181608def6412eb57beaa3d481533cff8b9e367a2485d5a4bf59fcf7

Tx prefix hash: 1358f34fa11913b1c0413423a9c6dbc49d897ad05d58211268b1a9f11dd61c45
Tx public key: 449c90ccdf1c09d9b9a9055bf7685597b783e5755ef949aae25b8a8ad99835d6
Timestamp: 1710013892 Timestamp [UCT]: 2024-03-09 19:51:32 Age [y:d:h:m:s]: 01:018:05:37:27
Block: 974773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274012 RingCT/type: yes/0
Extra: 01449c90ccdf1c09d9b9a9055bf7685597b783e5755ef949aae25b8a8ad99835d60211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e6127271e8aa082103c055f53f9485e94049a041bd360324079e9ef1cf671ae 0.600000000000 1434732 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": 974783, "vin": [ { "gen": { "height": 974773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e6127271e8aa082103c055f53f9485e94049a041bd360324079e9ef1cf671ae" } } ], "extra": [ 1, 68, 156, 144, 204, 223, 28, 9, 217, 185, 169, 5, 91, 247, 104, 85, 151, 183, 131, 229, 117, 94, 249, 73, 170, 226, 91, 138, 138, 217, 152, 53, 214, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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