Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f84b0906e258b5a453fe4c1adca7c4a6f9d8c13c1acad327bbecd4b5a88afe9

Tx prefix hash: ebbac79b46d67f911ea69f790c9db8f7bfdcc29a47a2fa240a329c29892e644d
Tx public key: 701ab387917bc56213bd9a197958ba4e6d3b853dc047e1afa060434fa3698f9b
Timestamp: 1754342183 Timestamp [UCT]: 2025-08-04 21:16:23 Age [y:d:h:m:s]: 00:114:22:05:15
Block: 1340347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81117 RingCT/type: yes/0
Extra: 01701ab387917bc56213bd9a197958ba4e6d3b853dc047e1afa060434fa3698f9b021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92c3b7961e08b7f53dde0258b2f739c15f7c3782c57bbb28b925a0d96e20edb0 0.600000000000 1828164 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": 1340357, "vin": [ { "gen": { "height": 1340347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92c3b7961e08b7f53dde0258b2f739c15f7c3782c57bbb28b925a0d96e20edb0" } } ], "extra": [ 1, 112, 26, 179, 135, 145, 123, 197, 98, 19, 189, 154, 25, 121, 88, 186, 78, 109, 59, 133, 61, 192, 71, 225, 175, 160, 96, 67, 79, 163, 105, 143, 155, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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