Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c61a6f2735977b8448f1e0582bd63f757e79edeb5ac9fd382e97847608d63732

Tx prefix hash: 5933839fd66f93b35c618b406831c5e7e4b1a110a54c62eaf0c17fe184803763
Tx public key: 35bd2622c40e64feddb3dd168aa7e69d1aa2847c89992e6d8e1ad31bd5f5b716
Timestamp: 1707025806 Timestamp [UCT]: 2024-02-04 05:50:06 Age [y:d:h:m:s]: 01:059:19:59:26
Block: 949978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303817 RingCT/type: yes/0
Extra: 0135bd2622c40e64feddb3dd168aa7e69d1aa2847c89992e6d8e1ad31bd5f5b71602110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de79563b8cefe9dd1ab44790b626a730ed9aa2913dfc66cde770fe08615dbe5a 0.600000000000 1408516 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": 949988, "vin": [ { "gen": { "height": 949978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de79563b8cefe9dd1ab44790b626a730ed9aa2913dfc66cde770fe08615dbe5a" } } ], "extra": [ 1, 53, 189, 38, 34, 196, 14, 100, 254, 221, 179, 221, 22, 138, 167, 230, 157, 26, 162, 132, 124, 137, 153, 46, 109, 142, 26, 211, 27, 213, 245, 183, 22, 2, 17, 0, 0, 0, 7, 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