Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b672de2551902895e235a8f514533a6ba91e0fa1a4dc2d53a81c31235c97b11a

Tx prefix hash: dc3705a0dc424a3425828ee7ba1ecc118c3e77030174cbb780e507209c37561f
Tx public key: 810f7d3c11b523bf4a9f139ff924a90010add2e6cb90f774bf238f1d057b0cc1
Timestamp: 1705690259 Timestamp [UCT]: 2024-01-19 18:50:59 Age [y:d:h:m:s]: 01:035:22:25:22
Block: 938892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286749 RingCT/type: yes/0
Extra: 01810f7d3c11b523bf4a9f139ff924a90010add2e6cb90f774bf238f1d057b0cc10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c93692a214d90f8057b418133b499ec0f44fa634a363cc924d968226b0b29cca 0.600000000000 1396974 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": 938902, "vin": [ { "gen": { "height": 938892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c93692a214d90f8057b418133b499ec0f44fa634a363cc924d968226b0b29cca" } } ], "extra": [ 1, 129, 15, 125, 60, 17, 181, 35, 191, 74, 159, 19, 159, 249, 36, 169, 0, 16, 173, 210, 230, 203, 144, 247, 116, 191, 35, 143, 29, 5, 123, 12, 193, 2, 17, 0, 0, 0, 1, 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