Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0264ad24abb10c31c8b90b6b6ab05df202ab8a60adfecbdd6817fea3a9bcdbb

Tx prefix hash: 4d0ae2ed5dc03533e9772e087bb53f4e9ca7a753317f93123e258a288c363300
Tx public key: 4731848c6691be81e2738ca2ea41a143c8340f47a4b1411c1d6f91817e2923c8
Timestamp: 1737770644 Timestamp [UCT]: 2025-01-25 02:04:04 Age [y:d:h:m:s]: 00:143:15:37:33
Block: 1204695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102410 RingCT/type: yes/0
Extra: 014731848c6691be81e2738ca2ea41a143c8340f47a4b1411c1d6f91817e2923c8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94a8c8197c6d7637d95241cfc2307e72295d70dc3e62b6245df265a27480295a 0.600000000000 1691386 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": 1204705, "vin": [ { "gen": { "height": 1204695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94a8c8197c6d7637d95241cfc2307e72295d70dc3e62b6245df265a27480295a" } } ], "extra": [ 1, 71, 49, 132, 140, 102, 145, 190, 129, 226, 115, 140, 162, 234, 65, 161, 67, 200, 52, 15, 71, 164, 177, 65, 28, 29, 111, 145, 129, 126, 41, 35, 200, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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