Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 120ee380317560040c5aac2a1afcafe7ee2a7099fdbfefe411773cbcf7e5f034

Tx prefix hash: 8fc57c92ba773738a26d5d457dc2a8b6403662afd0f7bee267316dd67ae14f64
Tx public key: f996368a713df20dd9931d6fd11ed755c30c5b1b5fdeb7d263b4e85d7ca97d13
Timestamp: 1703882524 Timestamp [UCT]: 2023-12-29 20:42:04 Age [y:d:h:m:s]: 01:013:06:27:27
Block: 923931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270811 RingCT/type: yes/0
Extra: 01f996368a713df20dd9931d6fd11ed755c30c5b1b5fdeb7d263b4e85d7ca97d1302110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc402e4a3f64032554f3739f9102645239e00edf576ff135a07f82a4133bf963 0.600000000000 1381669 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": 923941, "vin": [ { "gen": { "height": 923931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc402e4a3f64032554f3739f9102645239e00edf576ff135a07f82a4133bf963" } } ], "extra": [ 1, 249, 150, 54, 138, 113, 61, 242, 13, 217, 147, 29, 111, 209, 30, 215, 85, 195, 12, 91, 27, 95, 222, 183, 210, 99, 180, 232, 93, 124, 169, 125, 19, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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