Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bf464e3bf8a5dad77a3f7d2ae621d516ff10774ec74401077a792d14b831358

Tx prefix hash: e54abcb49fed35dfc3c43edc478b6123600a18f18287d96aed0eaff78531c766
Tx public key: e06e48387e7c2d97e09ad914349280ed4ab6c1ee2a7df598f8e17d2bea09462c
Timestamp: 1764134389 Timestamp [UCT]: 2025-11-26 05:19:49 Age [y:d:h:m:s]: 00:026:07:22:30
Block: 1420317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18839 RingCT/type: yes/0
Extra: 01e06e48387e7c2d97e09ad914349280ed4ab6c1ee2a7df598f8e17d2bea09462c0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc5c543992e7f06ec8e62cbce65bb0af83ae4a583090f3732d519c0a96d858c7 0.600000000000 1908860 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": 1420327, "vin": [ { "gen": { "height": 1420317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc5c543992e7f06ec8e62cbce65bb0af83ae4a583090f3732d519c0a96d858c7" } } ], "extra": [ 1, 224, 110, 72, 56, 126, 124, 45, 151, 224, 154, 217, 20, 52, 146, 128, 237, 74, 182, 193, 238, 42, 125, 245, 152, 248, 225, 125, 43, 234, 9, 70, 44, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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