Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3adedc18409d1362036dce7d89e16519d6468eda7065d2959c89e8009507eff0

Tx prefix hash: 3f119e7d9e73d4a562f1e8f4de15f7ab2d741ce19689d03045dbd0c27257dbc7
Tx public key: 8bf6f11f7a96e1fa55a627808d01d0cb4538987defa0160e27a7f7bca1d6001e
Timestamp: 1709082263 Timestamp [UCT]: 2024-02-28 01:04:23 Age [y:d:h:m:s]: 01:041:21:32:21
Block: 967053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290945 RingCT/type: yes/0
Extra: 018bf6f11f7a96e1fa55a627808d01d0cb4538987defa0160e27a7f7bca1d6001e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 907a07bce809d906b92638b85eac27f196c9eb2e6f42dff0daa96e5c79e13dc5 0.600000000000 1426824 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": 967063, "vin": [ { "gen": { "height": 967053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "907a07bce809d906b92638b85eac27f196c9eb2e6f42dff0daa96e5c79e13dc5" } } ], "extra": [ 1, 139, 246, 241, 31, 122, 150, 225, 250, 85, 166, 39, 128, 141, 1, 208, 203, 69, 56, 152, 125, 239, 160, 22, 14, 39, 167, 247, 188, 161, 214, 0, 30, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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