Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6d9b8c5fbf0eb2777d147bd7244689341a257f1ba7f3804668d13e07b03ccec

Tx prefix hash: de12e9832437f974b9b3010e4adeaf67df5bf91f1ebd1e492fdfbfa3ce2b0ff0
Tx public key: f20350c14ed9f944a1ba8efafcca8fc32831c82ed3911c382c1743d067499d6a
Timestamp: 1711641580 Timestamp [UCT]: 2024-03-28 15:59:40 Age [y:d:h:m:s]: 01:042:07:40:42
Block: 988280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291210 RingCT/type: yes/0
Extra: 01f20350c14ed9f944a1ba8efafcca8fc32831c82ed3911c382c1743d067499d6a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 858b64324170aa9199ba35f7dfdeb784e268d8f756fca7c63dd9b9727420ed8f 0.600000000000 1448555 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": 988290, "vin": [ { "gen": { "height": 988280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "858b64324170aa9199ba35f7dfdeb784e268d8f756fca7c63dd9b9727420ed8f" } } ], "extra": [ 1, 242, 3, 80, 193, 78, 217, 249, 68, 161, 186, 142, 250, 252, 202, 143, 195, 40, 49, 200, 46, 211, 145, 28, 56, 44, 23, 67, 208, 103, 73, 157, 106, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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