Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f42772459c9e3306f622a16bad1ab3323a26e894bf2c7bef053c0d0bf40d515b

Tx prefix hash: 45c9640361590f7e5a6ed618fbf6e02f6352b4dd4ddef69119bf9a7ef14992cd
Tx public key: baea39909278ffc18a0900d44fc6e3d649e2a3ad27eba45a78a1f41a2db91c36
Timestamp: 1724165130 Timestamp [UCT]: 2024-08-20 14:45:30 Age [y:d:h:m:s]: 00:229:23:11:16
Block: 1092093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164206 RingCT/type: yes/0
Extra: 01baea39909278ffc18a0900d44fc6e3d649e2a3ad27eba45a78a1f41a2db91c36021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e891ae3d9676721297a111805380046c7855d9685ba477c0d1c3853c22b64c1 0.600000000000 1566770 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": 1092103, "vin": [ { "gen": { "height": 1092093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e891ae3d9676721297a111805380046c7855d9685ba477c0d1c3853c22b64c1" } } ], "extra": [ 1, 186, 234, 57, 144, 146, 120, 255, 193, 138, 9, 0, 212, 79, 198, 227, 214, 73, 226, 163, 173, 39, 235, 164, 90, 120, 161, 244, 26, 45, 185, 28, 54, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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