Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7825bf908eaf9c4e9507f460a1b1eae3cc5ed34251221352320349868f3ee216

Tx prefix hash: 3b4863362d9655cb8d6e14f98e69e0a277c4872a965950ae271b076be45d3644
Tx public key: 17c31d6ff04fdbc2a4f2868f03b2229cff870ab5840916e89f7e531e68d62669
Timestamp: 1738796686 Timestamp [UCT]: 2025-02-05 23:04:46 Age [y:d:h:m:s]: 00:288:17:50:56
Block: 1212948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204131 RingCT/type: yes/0
Extra: 0117c31d6ff04fdbc2a4f2868f03b2229cff870ab5840916e89f7e531e68d626690211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d59488bcf1296f7b11abb6b1ad1c6df3f6fa9690189167f9ca4fdb2f8c35a263 0.600000000000 1699723 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": 1212958, "vin": [ { "gen": { "height": 1212948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d59488bcf1296f7b11abb6b1ad1c6df3f6fa9690189167f9ca4fdb2f8c35a263" } } ], "extra": [ 1, 23, 195, 29, 111, 240, 79, 219, 194, 164, 242, 134, 143, 3, 178, 34, 156, 255, 135, 10, 181, 132, 9, 22, 232, 159, 126, 83, 30, 104, 214, 38, 105, 2, 17, 0, 0, 0, 6, 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