Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66814b98563a336be157db7ada200732e932e2943271317703821af68f2a0c46

Tx prefix hash: f93cb3515cee732877c77223b2e95a4d33e6bc53a4854b0b328a708a36cb17d7
Tx public key: dcb275d17fce2a5c6941db0fb0ba8ccb82605b872cd8ed70dde12a8d98327122
Timestamp: 1737448009 Timestamp [UCT]: 2025-01-21 08:26:49 Age [y:d:h:m:s]: 00:150:23:29:43
Block: 1202013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107598 RingCT/type: yes/0
Extra: 01dcb275d17fce2a5c6941db0fb0ba8ccb82605b872cd8ed70dde12a8d983271220211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16c20beef2580c85731c738a2e23f179541f079ba9c4b7107510d43efe2b8e7f 0.600000000000 1688672 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": 1202023, "vin": [ { "gen": { "height": 1202013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16c20beef2580c85731c738a2e23f179541f079ba9c4b7107510d43efe2b8e7f" } } ], "extra": [ 1, 220, 178, 117, 209, 127, 206, 42, 92, 105, 65, 219, 15, 176, 186, 140, 203, 130, 96, 91, 135, 44, 216, 237, 112, 221, 225, 42, 141, 152, 50, 113, 34, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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