Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74562a1c349673b0897e951454536dfe15cdd30ae83bad17d6c6910b286028f8

Tx prefix hash: 0acb22cd277ecb7627002eb91e4f6e6e61349543f0bb8ee66c35c71ad81bc0ed
Tx public key: ab61e0b9a5067a3e600a64c6316eec2d4d62c3a9733d674774e7d1ec7f9243af
Timestamp: 1729929948 Timestamp [UCT]: 2024-10-26 08:05:48 Age [y:d:h:m:s]: 00:218:10:55:08
Block: 1139852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155961 RingCT/type: yes/0
Extra: 01ab61e0b9a5067a3e600a64c6316eec2d4d62c3a9733d674774e7d1ec7f9243af0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dac1122ddf68142a339cc4745b35bd04053b853b926da2b005e0806b770a5b7 0.600000000000 1623639 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": 1139862, "vin": [ { "gen": { "height": 1139852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dac1122ddf68142a339cc4745b35bd04053b853b926da2b005e0806b770a5b7" } } ], "extra": [ 1, 171, 97, 224, 185, 165, 6, 122, 62, 96, 10, 100, 198, 49, 110, 236, 45, 77, 98, 195, 169, 115, 61, 103, 71, 116, 231, 209, 236, 127, 146, 67, 175, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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