Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7925a4216702dd6fdd1f1d504af1573090244fe50c88ce8e29d1cec130a7499e

Tx prefix hash: f5c5314b20f4cffc3945cc55e835cae150d4126c15d78af22087f6bab93c7f22
Tx public key: a02ae0e3b50f59f1b01fa4e06c6c955283747f6ff5779ef7b01e005eb57d9bab
Timestamp: 1716271638 Timestamp [UCT]: 2024-05-21 06:07:18 Age [y:d:h:m:s]: 01:025:23:40:14
Block: 1026653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279388 RingCT/type: yes/0
Extra: 01a02ae0e3b50f59f1b01fa4e06c6c955283747f6ff5779ef7b01e005eb57d9bab0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c982843313e49b1b3fd321e596e1418ddc431ee3c6cfb12cbfbf30512e2da9d5 0.600000000000 1493854 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": 1026663, "vin": [ { "gen": { "height": 1026653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c982843313e49b1b3fd321e596e1418ddc431ee3c6cfb12cbfbf30512e2da9d5" } } ], "extra": [ 1, 160, 42, 224, 227, 181, 15, 89, 241, 176, 31, 164, 224, 108, 108, 149, 82, 131, 116, 127, 111, 245, 119, 158, 247, 176, 30, 0, 94, 181, 125, 155, 171, 2, 17, 0, 0, 0, 2, 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