Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2590d93685d518f30a757f742221a0ef9bac2505079c31affc8573a857073dc

Tx prefix hash: 691abb6da83685554e0478d23c75f7711b236164bf5c5bbd7cea36b59c65731f
Tx public key: e8ffcb6a7b1ce63b7e71b75535b38fe372df450a0a79c624f3e7419e6eeb691c
Timestamp: 1734777067 Timestamp [UCT]: 2024-12-21 10:31:07 Age [y:d:h:m:s]: 00:103:15:22:26
Block: 1179976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73821 RingCT/type: yes/0
Extra: 01e8ffcb6a7b1ce63b7e71b75535b38fe372df450a0a79c624f3e7419e6eeb691c0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7416f7d23d549fe8d15bbd52cd1e3257c9eac1aabadeceeac27192d05639cda 0.600000000000 1666379 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": 1179986, "vin": [ { "gen": { "height": 1179976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7416f7d23d549fe8d15bbd52cd1e3257c9eac1aabadeceeac27192d05639cda" } } ], "extra": [ 1, 232, 255, 203, 106, 123, 28, 230, 59, 126, 113, 183, 85, 53, 179, 143, 227, 114, 223, 69, 10, 10, 121, 198, 36, 243, 231, 65, 158, 110, 235, 105, 28, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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