Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d10adbdb917116d259a5fa1477947a2321000ac1d9df7298e0cc6b6a56b0c1a1

Tx prefix hash: 97af4bbe34c9522baa6779ee7b7a29d072088b3902e42faef128eaeb10053802
Tx public key: 3fa8b90ac6b0af2136104c0014c63051f4cc3107f7edd3f830e2e796dfdd428e
Timestamp: 1702803470 Timestamp [UCT]: 2023-12-17 08:57:50 Age [y:d:h:m:s]: 01:109:05:18:34
Block: 914988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339190 RingCT/type: yes/0
Extra: 013fa8b90ac6b0af2136104c0014c63051f4cc3107f7edd3f830e2e796dfdd428e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d849749d3a628431bc35fba895e7fbc00471ac5b4e5e485abf26fff7b128b0d4 0.600000000000 1372354 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": 914998, "vin": [ { "gen": { "height": 914988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d849749d3a628431bc35fba895e7fbc00471ac5b4e5e485abf26fff7b128b0d4" } } ], "extra": [ 1, 63, 168, 185, 10, 198, 176, 175, 33, 54, 16, 76, 0, 20, 198, 48, 81, 244, 204, 49, 7, 247, 237, 211, 248, 48, 226, 231, 150, 223, 221, 66, 142, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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