Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa8b2fe8e6d053db8dbda0fa2921ab636501ddcd4805593d5e33738e47b1ead

Tx prefix hash: f0264898f88a126cb09ef6be1432670e4e3aa112c1e00fa20477e3c58c68cf3e
Tx public key: ccc147dc852b55643d2eef5e736c48d6783f541386b760d30e02593a0ad5a1a9
Timestamp: 1707705809 Timestamp [UCT]: 2024-02-12 02:43:29 Age [y:d:h:m:s]: 01:294:01:20:43
Block: 955619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468962 RingCT/type: yes/0
Extra: 01ccc147dc852b55643d2eef5e736c48d6783f541386b760d30e02593a0ad5a1a90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9626cd6f156e5c4e95f12f06e739ee644598c346361c34ce12ac70ce6b1c7a26 0.600000000000 1414917 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": 955629, "vin": [ { "gen": { "height": 955619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9626cd6f156e5c4e95f12f06e739ee644598c346361c34ce12ac70ce6b1c7a26" } } ], "extra": [ 1, 204, 193, 71, 220, 133, 43, 85, 100, 61, 46, 239, 94, 115, 108, 72, 214, 120, 63, 84, 19, 134, 183, 96, 211, 14, 2, 89, 58, 10, 213, 161, 169, 2, 17, 0, 0, 0, 1, 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