Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bcd5d570df435a541203ca2d9255cff750589a13af1b7f991f0c5545e60c271

Tx prefix hash: b88de7c656554772c13223563e85bb7266a15bc0a6aaae2dd59ef97bd2a8bd6b
Tx public key: 750bf5bfb1aa6c34437a9aa04b6220d9b979087eaeb03d5e53ef74b9a27489e4
Timestamp: 1706374957 Timestamp [UCT]: 2024-01-27 17:02:37 Age [y:d:h:m:s]: 01:100:09:39:19
Block: 944574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332861 RingCT/type: yes/0
Extra: 01750bf5bfb1aa6c34437a9aa04b6220d9b979087eaeb03d5e53ef74b9a27489e402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e696ead74261cf3c4eb50208d3e12a55f054c22055ebbb4279ae48e16a722933 0.600000000000 1402856 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": 944584, "vin": [ { "gen": { "height": 944574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e696ead74261cf3c4eb50208d3e12a55f054c22055ebbb4279ae48e16a722933" } } ], "extra": [ 1, 117, 11, 245, 191, 177, 170, 108, 52, 67, 122, 154, 160, 75, 98, 32, 217, 185, 121, 8, 126, 174, 176, 61, 94, 83, 239, 116, 185, 162, 116, 137, 228, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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