Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df74b117d2147cb6cc4e317c937f058c1a3a06c15d35ff76127ecd4976bc3dd9

Tx prefix hash: 6be993b8634d12f4e2e9c69df2eb66677a86bd20ce5441f810a351705b5326dd
Tx public key: 69b0a76e966afe729635bd5dff178350ccd0fc8eb4fde41759763b8c84c0602a
Timestamp: 1713840135 Timestamp [UCT]: 2024-04-23 02:42:15 Age [y:d:h:m:s]: 01:191:18:21:17
Block: 1006486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395697 RingCT/type: yes/0
Extra: 0169b0a76e966afe729635bd5dff178350ccd0fc8eb4fde41759763b8c84c0602a02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aa61e2075b22154f8c8e623256d44b2b26efe57778b71aad3014df716b22a0d 0.600000000000 1467532 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": 1006496, "vin": [ { "gen": { "height": 1006486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aa61e2075b22154f8c8e623256d44b2b26efe57778b71aad3014df716b22a0d" } } ], "extra": [ 1, 105, 176, 167, 110, 150, 106, 254, 114, 150, 53, 189, 93, 255, 23, 131, 80, 204, 208, 252, 142, 180, 253, 228, 23, 89, 118, 59, 140, 132, 192, 96, 42, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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