Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 207ddacbcf2b99fef2833a75abec80f913c11cf833288861185afc964932fca9

Tx prefix hash: fa92f76627d8e320de9e89f51f8441ad9191d66083575b94e62b65dd6dd42d83
Tx public key: f1f18866a6a7549e81d6f13c27a7ef9c2c09eff193ec3ba95e0a4725cb4ea6d8
Timestamp: 1724965106 Timestamp [UCT]: 2024-08-29 20:58:26 Age [y:d:h:m:s]: 00:055:01:27:27
Block: 1098713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39419 RingCT/type: yes/0
Extra: 01f1f18866a6a7549e81d6f13c27a7ef9c2c09eff193ec3ba95e0a4725cb4ea6d802110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a64fadfa693ce6c2e80bd064bdcc71eeb655c5128af9997ad6dc8acd804cd24b 0.600000000000 1574524 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": 1098723, "vin": [ { "gen": { "height": 1098713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a64fadfa693ce6c2e80bd064bdcc71eeb655c5128af9997ad6dc8acd804cd24b" } } ], "extra": [ 1, 241, 241, 136, 102, 166, 167, 84, 158, 129, 214, 241, 60, 39, 167, 239, 156, 44, 9, 239, 241, 147, 236, 59, 169, 94, 10, 71, 37, 203, 78, 166, 216, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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