Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b832b44719138834680ef0a95a69ad8b4e09088bf1dc2c1b338390b3833f40bb

Tx prefix hash: 9ce75554af6d87f25f13358516964e57a0fb5933e74170fe4787714eafc0865f
Tx public key: 1b6a9ae64f44a20d6f840f76355be111c95970c4fcae460c8390a0c9c38c3a7f
Timestamp: 1634246788 Timestamp [UCT]: 2021-10-14 21:26:28 Age [y:d:h:m:s]: 03:035:23:09:42
Block: 353125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 803500 RingCT/type: yes/0
Extra: 011b6a9ae64f44a20d6f840f76355be111c95970c4fcae460c8390a0c9c38c3a7f0211000000335410958b000000000000000000

1 output(s) for total of 41.490694542000 dcy

stealth address amount amount idx
00: e44972573e23a76bf4957273f14b4940069062d96a7a51575a2772b5616f85ef 41.490694542000 721643 of 0

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": 353135, "vin": [ { "gen": { "height": 353125 } } ], "vout": [ { "amount": 41490694542, "target": { "key": "e44972573e23a76bf4957273f14b4940069062d96a7a51575a2772b5616f85ef" } } ], "extra": [ 1, 27, 106, 154, 230, 79, 68, 162, 13, 111, 132, 15, 118, 53, 91, 225, 17, 201, 89, 112, 196, 252, 174, 70, 12, 131, 144, 160, 201, 195, 140, 58, 127, 2, 17, 0, 0, 0, 51, 84, 16, 149, 139, 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