Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79e26a40ef98c1b038863c7412a37811dff393439ec1a1a945a267ea72e1ddc7

Tx prefix hash: 1592d8bc60e7dcda63d718aeb3d7f5fa1428a004a938038d9ef52d87f37f4296
Tx public key: 603fadd374f40baa39b2aa7013d098e6828a7fcf589822294c5402843e2ab7e5
Timestamp: 1728158944 Timestamp [UCT]: 2024-10-05 20:09:04 Age [y:d:h:m:s]: 00:204:02:26:01
Block: 1125198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145683 RingCT/type: yes/0
Extra: 01603fadd374f40baa39b2aa7013d098e6828a7fcf589822294c5402843e2ab7e502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f0abaff651b07079dc5f3d1fead0c43d374f90c462363395c70c504984a5110 0.600000000000 1607875 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": 1125208, "vin": [ { "gen": { "height": 1125198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f0abaff651b07079dc5f3d1fead0c43d374f90c462363395c70c504984a5110" } } ], "extra": [ 1, 96, 63, 173, 211, 116, 244, 11, 170, 57, 178, 170, 112, 19, 208, 152, 230, 130, 138, 127, 207, 88, 152, 34, 41, 76, 84, 2, 132, 62, 42, 183, 229, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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