Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7f8667c1ca120cb650dfeed20e6d08e349cbde20d5ce82a61ee244bdefe10b9

Tx prefix hash: beed9f5c77ef7cfa0b7a0ec910e24e83d6601b7378c42ed65581882e1ef0abed
Tx public key: 7f620ab2db37bd9e49766ee0b4c9a7af91c80e6a301ccddc290c7120664b4863
Timestamp: 1723607384 Timestamp [UCT]: 2024-08-14 03:49:44 Age [y:d:h:m:s]: 01:090:01:43:16
Block: 1087461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322842 RingCT/type: yes/0
Extra: 017f620ab2db37bd9e49766ee0b4c9a7af91c80e6a301ccddc290c7120664b4863021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82a2cf9794d0dfad1ca7890c2b54d74546dc3027319aedbf4bc9a6f144376496 0.600000000000 1562070 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": 1087471, "vin": [ { "gen": { "height": 1087461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82a2cf9794d0dfad1ca7890c2b54d74546dc3027319aedbf4bc9a6f144376496" } } ], "extra": [ 1, 127, 98, 10, 178, 219, 55, 189, 158, 73, 118, 110, 224, 180, 201, 167, 175, 145, 200, 14, 106, 48, 28, 205, 220, 41, 12, 113, 32, 102, 75, 72, 99, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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