Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd9beca80ecce82949954af1e3fa687b7f041f992075eb4d32f16b216c5fbfdc

Tx prefix hash: 47499433a6caa1447843ed06562457e28f761b8227afdb98345c75c2127cf3a0
Tx public key: ac1a43088ac81f769666c3332dc1d23408cdabdca335bfd402cf03b0a5a52741
Timestamp: 1736407349 Timestamp [UCT]: 2025-01-09 07:22:29 Age [y:d:h:m:s]: 00:291:15:49:22
Block: 1193442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205948 RingCT/type: yes/0
Extra: 01ac1a43088ac81f769666c3332dc1d23408cdabdca335bfd402cf03b0a5a5274102110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6c5e841352a31b51bdc5670c95e587d274ba7b0eb65b0e509e66ae6af16f271 0.600000000000 1680003 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": 1193452, "vin": [ { "gen": { "height": 1193442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6c5e841352a31b51bdc5670c95e587d274ba7b0eb65b0e509e66ae6af16f271" } } ], "extra": [ 1, 172, 26, 67, 8, 138, 200, 31, 118, 150, 102, 195, 51, 45, 193, 210, 52, 8, 205, 171, 220, 163, 53, 191, 212, 2, 207, 3, 176, 165, 165, 39, 65, 2, 17, 0, 0, 0, 12, 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