Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f85c9de7d546ae419d884260d583855b4f2b9ff9606a1c213c6d6434da71efc

Tx prefix hash: 6014f2c3b2bc74a8e4f2cdc442e26cb1489612d9df13490b2499e8d0380a6d33
Tx public key: 330f2361f5dd4279a96aeb89b9183129dd0a29340d2a3d680179217e7161401d
Timestamp: 1763321278 Timestamp [UCT]: 2025-11-16 19:27:58 Age [y:d:h:m:s]: 00:076:16:47:40
Block: 1413582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54731 RingCT/type: yes/0
Extra: 01330f2361f5dd4279a96aeb89b9183129dd0a29340d2a3d680179217e7161401d021100000002defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54ffdc33b53ef0c9d78b95f62d8c58f29b7c600820c350da111958c60ac544a0 0.600000000000 1902061 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": 1413592, "vin": [ { "gen": { "height": 1413582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54ffdc33b53ef0c9d78b95f62d8c58f29b7c600820c350da111958c60ac544a0" } } ], "extra": [ 1, 51, 15, 35, 97, 245, 221, 66, 121, 169, 106, 235, 137, 185, 24, 49, 41, 221, 10, 41, 52, 13, 42, 61, 104, 1, 121, 33, 126, 113, 97, 64, 29, 2, 17, 0, 0, 0, 2, 222, 251, 143, 24, 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