Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d1a05d00df596ed6e74b12185f3eeac642e33c5c9721c05fe79e8b7c85758bd

Tx prefix hash: 3423a34f2847b4c529c10c30dc8485d4232df4c24f8dfbb94c37c5389a3cbc14
Tx public key: 4be94efc9aede2309fb319d7284850bab33ee6dab9029738a22b8c8b33a7edc8
Timestamp: 1743893282 Timestamp [UCT]: 2025-04-05 22:48:02 Age [y:d:h:m:s]: 00:229:01:33:14
Block: 1255140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161438 RingCT/type: yes/0
Extra: 014be94efc9aede2309fb319d7284850bab33ee6dab9029738a22b8c8b33a7edc80211000000026c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e76a615c9e9e6174b7f7556b7856c62214da10323dddbaf0399f30377216eb9d 0.600000000000 1742243 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": 1255150, "vin": [ { "gen": { "height": 1255140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e76a615c9e9e6174b7f7556b7856c62214da10323dddbaf0399f30377216eb9d" } } ], "extra": [ 1, 75, 233, 78, 252, 154, 237, 226, 48, 159, 179, 25, 215, 40, 72, 80, 186, 179, 62, 230, 218, 185, 2, 151, 56, 162, 43, 140, 139, 51, 167, 237, 200, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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