Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33fee1837e3ca7d3edf15dcfb9c50c606c2257c22b098ce47a7550c1844f205a

Tx prefix hash: aa96c417ee5c7ef2f524754200c8c8bac0948caf5ea4d097c474d6ee00eca1e1
Tx public key: a1dfb72314fec2ea06f804ba0edaf1989d94273ffff8d04cfdf4f0ba67e055cf
Timestamp: 1721254792 Timestamp [UCT]: 2024-07-17 22:19:52 Age [y:d:h:m:s]: 00:097:22:55:38
Block: 1067968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70124 RingCT/type: yes/0
Extra: 01a1dfb72314fec2ea06f804ba0edaf1989d94273ffff8d04cfdf4f0ba67e055cf02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af9264f7ada0d3afcd8352739a9dd66d8426f687da6d9dab56051724c18e0d33 0.600000000000 1538929 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": 1067978, "vin": [ { "gen": { "height": 1067968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af9264f7ada0d3afcd8352739a9dd66d8426f687da6d9dab56051724c18e0d33" } } ], "extra": [ 1, 161, 223, 183, 35, 20, 254, 194, 234, 6, 248, 4, 186, 14, 218, 241, 152, 157, 148, 39, 63, 255, 248, 208, 76, 253, 244, 240, 186, 103, 224, 85, 207, 2, 17, 0, 0, 0, 4, 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