Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e25d1439292ea139ad754311c9d5f3c93cf975e67a709e3a7a2c81fcc793a9c

Tx prefix hash: 32f2d6d3996e449ab94fef18bafa786cb5f5e64446deab89fa3e30389ab5f5e1
Tx public key: fbc7919e87eb3628681a1b5449ecf5d7173594e395b9a3573161062a10cc6b1c
Timestamp: 1675623747 Timestamp [UCT]: 2023-02-05 19:02:27 Age [y:d:h:m:s]: 02:067:05:49:41
Block: 690542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569669 RingCT/type: yes/0
Extra: 01fbc7919e87eb3628681a1b5449ecf5d7173594e395b9a3573161062a10cc6b1c0211000000015029cbac000000000000000000

1 output(s) for total of 3.161896308000 dcy

stealth address amount amount idx
00: dca45f491787f96a0896158e01e12fd587a43cb07ed88204ea8f1e786ff72e23 3.161896308000 1133272 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": 690552, "vin": [ { "gen": { "height": 690542 } } ], "vout": [ { "amount": 3161896308, "target": { "key": "dca45f491787f96a0896158e01e12fd587a43cb07ed88204ea8f1e786ff72e23" } } ], "extra": [ 1, 251, 199, 145, 158, 135, 235, 54, 40, 104, 26, 27, 84, 73, 236, 245, 215, 23, 53, 148, 227, 149, 185, 163, 87, 49, 97, 6, 42, 16, 204, 107, 28, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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