Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c563735f00acb69f583a289812e9c4e24c38f14cd12c826f33f92d0b235ccc0

Tx prefix hash: 019417cbbbd1e54749befebba1c03fe85f1b62bbf7f6ec1d961ee55afc7f555e
Tx public key: 65ba67c8c5f71a144a0687bb271220b15c29efd5d8721f4092cfdba10f33c87c
Timestamp: 1723736647 Timestamp [UCT]: 2024-08-15 15:44:07 Age [y:d:h:m:s]: 00:239:10:57:11
Block: 1088537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171020 RingCT/type: yes/0
Extra: 0165ba67c8c5f71a144a0687bb271220b15c29efd5d8721f4092cfdba10f33c87c02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f15ba2a5d9c524699b056e3e7cd1da1c2ab15b36b614d79bf617066c78eb5ab9 0.600000000000 1563154 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": 1088547, "vin": [ { "gen": { "height": 1088537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f15ba2a5d9c524699b056e3e7cd1da1c2ab15b36b614d79bf617066c78eb5ab9" } } ], "extra": [ 1, 101, 186, 103, 200, 197, 247, 26, 20, 74, 6, 135, 187, 39, 18, 32, 177, 92, 41, 239, 213, 216, 114, 31, 64, 146, 207, 219, 161, 15, 51, 200, 124, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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