Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e43b9c2f93b6ca4bf79e8aabab90b5844feecdd887505239b0ec91823e487509

Tx prefix hash: 4ab44ab7781872811da7138ab458c17b42a9998b8cd1afe4abfc837937f2eb28
Tx public key: badaa8b8b3e00ae7635f1ad38d62fdd0c8d0bf404959e9f10f70b6d03adcb1a1
Timestamp: 1708406703 Timestamp [UCT]: 2024-02-20 05:25:03 Age [y:d:h:m:s]: 01:260:10:51:32
Block: 961439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 444875 RingCT/type: yes/0
Extra: 01badaa8b8b3e00ae7635f1ad38d62fdd0c8d0bf404959e9f10f70b6d03adcb1a10211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8aa759cab959fa8fed7df97fab764161b53f007a416ca49403896aaa35821bd 0.600000000000 1421048 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": 961449, "vin": [ { "gen": { "height": 961439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8aa759cab959fa8fed7df97fab764161b53f007a416ca49403896aaa35821bd" } } ], "extra": [ 1, 186, 218, 168, 184, 179, 224, 10, 231, 99, 95, 26, 211, 141, 98, 253, 208, 200, 208, 191, 64, 73, 89, 233, 241, 15, 112, 182, 208, 58, 220, 177, 161, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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