Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d05fab4b4c8bae6b4e31e9ad4ecf764bc2e2a29c4cd731933c7ebae2c8ad33a6

Tx prefix hash: 985ced908d5f67f70fdb53e3cc4a2760a012ece0f5e0041ebbe2dcdab41d6c1a
Tx public key: db2b214655e6502a2d8d0ad33dd4aa8d40c863ed20ad3df072568127947957ff
Timestamp: 1708598595 Timestamp [UCT]: 2024-02-22 10:43:15 Age [y:d:h:m:s]: 01:059:07:27:46
Block: 963033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303413 RingCT/type: yes/0
Extra: 01db2b214655e6502a2d8d0ad33dd4aa8d40c863ed20ad3df072568127947957ff0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f82894e1854ba2d632e64021d0aac4c402ce67142a7028e9262d7ff98f1bffe 0.600000000000 1422730 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": 963043, "vin": [ { "gen": { "height": 963033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f82894e1854ba2d632e64021d0aac4c402ce67142a7028e9262d7ff98f1bffe" } } ], "extra": [ 1, 219, 43, 33, 70, 85, 230, 80, 42, 45, 141, 10, 211, 61, 212, 170, 141, 64, 200, 99, 237, 32, 173, 61, 240, 114, 86, 129, 39, 148, 121, 87, 255, 2, 17, 0, 0, 0, 4, 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