Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4ff7d03e3bf318377b8fa483e80a494771225c90b32d6a9f3b1c808a859a654

Tx prefix hash: 06a7ce910912e0ca4733ecbed1d1905d41b6d6433bea21f2c6bfd9966448fa71
Tx public key: 3ad3e98b77dc8d1f893e747121b7a92140c4f6ab3a130580d8345db285cb9551
Timestamp: 1718538274 Timestamp [UCT]: 2024-06-16 11:44:34 Age [y:d:h:m:s]: 00:221:01:43:11
Block: 1045447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158149 RingCT/type: yes/0
Extra: 013ad3e98b77dc8d1f893e747121b7a92140c4f6ab3a130580d8345db285cb95510211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34dab4339d0db8dacf204087c7c818d4cdfdb14855acbd03a56367d83d3d5e61 0.600000000000 1515022 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": 1045457, "vin": [ { "gen": { "height": 1045447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34dab4339d0db8dacf204087c7c818d4cdfdb14855acbd03a56367d83d3d5e61" } } ], "extra": [ 1, 58, 211, 233, 139, 119, 220, 141, 31, 137, 62, 116, 113, 33, 183, 169, 33, 64, 196, 246, 171, 58, 19, 5, 128, 216, 52, 93, 178, 133, 203, 149, 81, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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