Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a72eb7f29387c436786cb0755589224c29523269ce4e9e8bc80ac32518c10d70

Tx prefix hash: 9a9e41a1879253273ea5d4198dd4d9c4d4beeeeed493720ed3a95976467b9d18
Tx public key: e906138f0f60a38f89aa57bbbc2cd055260b6dd0ef367275c39bd9f98084e62c
Timestamp: 1731225183 Timestamp [UCT]: 2024-11-10 07:53:03 Age [y:d:h:m:s]: 00:142:05:42:45
Block: 1150525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101476 RingCT/type: yes/0
Extra: 01e906138f0f60a38f89aa57bbbc2cd055260b6dd0ef367275c39bd9f98084e62c0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bd394d9f2317cc9c6281a2c8ea0f0bd9d42e2b1ad13a93e96db2c1764d19341 0.600000000000 1635864 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": 1150535, "vin": [ { "gen": { "height": 1150525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bd394d9f2317cc9c6281a2c8ea0f0bd9d42e2b1ad13a93e96db2c1764d19341" } } ], "extra": [ 1, 233, 6, 19, 143, 15, 96, 163, 143, 137, 170, 87, 187, 188, 44, 208, 85, 38, 11, 109, 208, 239, 54, 114, 117, 195, 155, 217, 249, 128, 132, 230, 44, 2, 17, 0, 0, 0, 5, 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