Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 663dd0d6ad1f076372d3669d6a055c44c876e275cabedc1bf16f865b85884ff5

Tx prefix hash: a6d10aef29f2751e20cbe424727beb481e1c3c93b229f183724af6c9ed14934d
Tx public key: ff864a0c8d3c9e76761d6bb33933ecebbd7e9a7c4e67ac53f192538283e6f15f
Timestamp: 1704033363 Timestamp [UCT]: 2023-12-31 14:36:03 Age [y:d:h:m:s]: 01:106:08:40:45
Block: 925177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337136 RingCT/type: yes/0
Extra: 01ff864a0c8d3c9e76761d6bb33933ecebbd7e9a7c4e67ac53f192538283e6f15f0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01baa32dc2989d634406a616c864037247a0c4e1f273ba36a20b75ad82202d76 0.600000000000 1382937 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": 925187, "vin": [ { "gen": { "height": 925177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01baa32dc2989d634406a616c864037247a0c4e1f273ba36a20b75ad82202d76" } } ], "extra": [ 1, 255, 134, 74, 12, 141, 60, 158, 118, 118, 29, 107, 179, 57, 51, 236, 235, 189, 126, 154, 124, 78, 103, 172, 83, 241, 146, 83, 130, 131, 230, 241, 95, 2, 17, 0, 0, 0, 9, 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