Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2394a6ba639bc716776d7510cd88a4f919f60fbe2678dc6ef7f968f59ae3782

Tx prefix hash: d4aa8745ee91260d3c16e6ffc11239e20b598affd0a9eeb66b62bd6c511211b5
Tx public key: 10e3bab732c5909c6d2fa59342865287c5f1c3f2db0640e8bdd9be64602beb01
Timestamp: 1710559467 Timestamp [UCT]: 2024-03-16 03:24:27 Age [y:d:h:m:s]: 01:024:08:21:34
Block: 979305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278379 RingCT/type: yes/0
Extra: 0110e3bab732c5909c6d2fa59342865287c5f1c3f2db0640e8bdd9be64602beb010211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 945d6750a0440081d630aae1714480d6653721fe80abf2e1584260802902ea35 0.600000000000 1439338 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": 979315, "vin": [ { "gen": { "height": 979305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "945d6750a0440081d630aae1714480d6653721fe80abf2e1584260802902ea35" } } ], "extra": [ 1, 16, 227, 186, 183, 50, 197, 144, 156, 109, 47, 165, 147, 66, 134, 82, 135, 197, 241, 195, 242, 219, 6, 64, 232, 189, 217, 190, 100, 96, 43, 235, 1, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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