Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 408139b1b4be2bcf630b2b446c3b5b00c878c3f5bf84136285a40262b80bcbdc

Tx prefix hash: b2e0f67b78c939209cf9fc0b54f7d601a01c33e3122cf151926ae36a7ef0b8c8
Tx public key: a5c93187b777546ae4c4aa22914d40be2fa94d707786f28d6e22e370a13d3c0b
Timestamp: 1711950054 Timestamp [UCT]: 2024-04-01 05:40:54 Age [y:d:h:m:s]: 01:045:17:49:23
Block: 990780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293711 RingCT/type: yes/0
Extra: 01a5c93187b777546ae4c4aa22914d40be2fa94d707786f28d6e22e370a13d3c0b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be9bafeb2ce57497c20034a85c242ad8245d124a65f517233992827c66746280 0.600000000000 1451108 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": 990790, "vin": [ { "gen": { "height": 990780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be9bafeb2ce57497c20034a85c242ad8245d124a65f517233992827c66746280" } } ], "extra": [ 1, 165, 201, 49, 135, 183, 119, 84, 106, 228, 196, 170, 34, 145, 77, 64, 190, 47, 169, 77, 112, 119, 134, 242, 141, 110, 34, 227, 112, 161, 61, 60, 11, 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