Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71629ebc378b239d09a5377a528691af8a6ba4378d6451358ac538d9d2bfb40c

Tx prefix hash: 348c48b9144d937de829e6bc1eb2af31bef3cd97b1a367fa89f8fcfe21cc17e8
Tx public key: 08ff51909d2b8d41351b5e0a42cf1a6848e3e6d32f91fb1b401329cd8c743b24
Timestamp: 1686485567 Timestamp [UCT]: 2023-06-11 12:12:47 Age [y:d:h:m:s]: 01:213:15:44:12
Block: 779967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414086 RingCT/type: yes/0
Extra: 0108ff51909d2b8d41351b5e0a42cf1a6848e3e6d32f91fb1b401329cd8c743b240211000000024b8f5122000000000000000000

1 output(s) for total of 1.598253663000 dcy

stealth address amount amount idx
00: e7006fe5668d6a9dfd2b2f69dcbecf19465457973a40ff407e7e333f9c7d0bcd 1.598253663000 1229656 of 0

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": 779977, "vin": [ { "gen": { "height": 779967 } } ], "vout": [ { "amount": 1598253663, "target": { "key": "e7006fe5668d6a9dfd2b2f69dcbecf19465457973a40ff407e7e333f9c7d0bcd" } } ], "extra": [ 1, 8, 255, 81, 144, 157, 43, 141, 65, 53, 27, 94, 10, 66, 207, 26, 104, 72, 227, 230, 211, 47, 145, 251, 27, 64, 19, 41, 205, 140, 116, 59, 36, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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