Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c727f3d34a178a1677e20a2ba4c02c1f3f0b215a0e2fe4e32441c429dcf3276b

Tx prefix hash: 1ced7c229fecabdbad89a9540caa8bc484d41db9d305821f54ef435e89bb21c0
Tx public key: 8058c9b4de512e4ce509e06a65dde222413a62aef80b887ca130f8355388da46
Timestamp: 1720696194 Timestamp [UCT]: 2024-07-11 11:09:54 Age [y:d:h:m:s]: 00:341:08:13:05
Block: 1063333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243817 RingCT/type: yes/0
Extra: 018058c9b4de512e4ce509e06a65dde222413a62aef80b887ca130f8355388da4602110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54b9fe5aacfff2a642913baeb7ae401bbd0c8099a2a602a25313f5ea82e012ff 0.600000000000 1533848 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": 1063343, "vin": [ { "gen": { "height": 1063333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54b9fe5aacfff2a642913baeb7ae401bbd0c8099a2a602a25313f5ea82e012ff" } } ], "extra": [ 1, 128, 88, 201, 180, 222, 81, 46, 76, 229, 9, 224, 106, 101, 221, 226, 34, 65, 58, 98, 174, 248, 11, 136, 124, 161, 48, 248, 53, 83, 136, 218, 70, 2, 17, 0, 0, 0, 8, 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