Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b782316981bfd0dbbf6365acd75c1c36e58fcd2c7423452230fb5aca575fd98c

Tx prefix hash: 042b2c023c4112f6def7f4fa9e0df6678dd2b03b13c6dede63b348b1bc6bc84d
Tx public key: 77af247a9bc5f447f8e323ce393dfb90394be539cd90eebbce8940cd8f31dc87
Timestamp: 1751655717 Timestamp [UCT]: 2025-07-04 19:01:57 Age [y:d:h:m:s]: 00:212:01:43:06
Block: 1318773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149808 RingCT/type: yes/0
Extra: 0177af247a9bc5f447f8e323ce393dfb90394be539cd90eebbce8940cd8f31dc8702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f8ea5b3d112b459e4e3f355922905a31d3e0763f78e2c436b21f38281b038c9 0.600000000000 1806460 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": 1318783, "vin": [ { "gen": { "height": 1318773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f8ea5b3d112b459e4e3f355922905a31d3e0763f78e2c436b21f38281b038c9" } } ], "extra": [ 1, 119, 175, 36, 122, 155, 197, 244, 71, 248, 227, 35, 206, 57, 61, 251, 144, 57, 75, 229, 57, 205, 144, 238, 187, 206, 137, 64, 205, 143, 49, 220, 135, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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