Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afe542bd2841514f89e1788613fac0bca8827c88774883f1fdd8d2190248567a

Tx prefix hash: 163f06c000e54e372e93e3701d72fe72c8028a1fa343aa7b54ff907ba6bf1224
Tx public key: 5ea058df3c346c22b68da65c2a678f91f478c11fbd1c872502362886157c0a94
Timestamp: 1713253557 Timestamp [UCT]: 2024-04-16 07:45:57 Age [y:d:h:m:s]: 00:211:03:06:16
Block: 1001601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151164 RingCT/type: yes/0
Extra: 015ea058df3c346c22b68da65c2a678f91f478c11fbd1c872502362886157c0a9402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76cc10e0d65e2e9c2c49d53dc8cffbfc8fac4c87a9c0192ba6c5a61e58d710d5 0.600000000000 1462107 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": 1001611, "vin": [ { "gen": { "height": 1001601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76cc10e0d65e2e9c2c49d53dc8cffbfc8fac4c87a9c0192ba6c5a61e58d710d5" } } ], "extra": [ 1, 94, 160, 88, 223, 60, 52, 108, 34, 182, 141, 166, 92, 42, 103, 143, 145, 244, 120, 193, 31, 189, 28, 135, 37, 2, 54, 40, 134, 21, 124, 10, 148, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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