Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4702b71034137696d42d19804cfe88f6695e40c95741a1c8a23b78b32838c48c

Tx prefix hash: a17a88655bfffe3194ded79d0b86cc42b6518229360f38c6eed6f186f80b3ea5
Tx public key: db801b7a1eef1bd39a93e9b3ebb5dbb11ba48c13eeab68729973b4a77f55718a
Timestamp: 1637280499 Timestamp [UCT]: 2021-11-19 00:08:19 Age [y:d:h:m:s]: 03:161:00:00:13
Block: 377304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893627 RingCT/type: yes/0
Extra: 01db801b7a1eef1bd39a93e9b3ebb5dbb11ba48c13eeab68729973b4a77f55718a02110000003b536c63bb000000000000000000

1 output(s) for total of 34.501911666000 dcy

stealth address amount amount idx
00: 38877b879e273a18cdd2a49c42e4c31d41617f0d3417d504c2b3963bc745346f 34.501911666000 763158 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": 377314, "vin": [ { "gen": { "height": 377304 } } ], "vout": [ { "amount": 34501911666, "target": { "key": "38877b879e273a18cdd2a49c42e4c31d41617f0d3417d504c2b3963bc745346f" } } ], "extra": [ 1, 219, 128, 27, 122, 30, 239, 27, 211, 154, 147, 233, 179, 235, 181, 219, 177, 27, 164, 140, 19, 238, 171, 104, 114, 153, 115, 180, 167, 127, 85, 113, 138, 2, 17, 0, 0, 0, 59, 83, 108, 99, 187, 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