Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b1d3c34c19ad349ef524f39b969860dd051bd3a34131ec4bc9766bbcece4838

Tx prefix hash: f6ea89326697e742cfab429a330d634ccd48ab8a1c4c4facf60f64b0113337ae
Tx public key: ece97584fd82ca08cdc37f46bb43e656aa8c81b4b8dff07838d857c70389b62a
Timestamp: 1657622102 Timestamp [UCT]: 2022-07-12 10:35:02 Age [y:d:h:m:s]: 02:252:00:14:02
Block: 542116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 701256 RingCT/type: yes/0
Extra: 01ece97584fd82ca08cdc37f46bb43e656aa8c81b4b8dff07838d857c70389b62a0211000000172e6b1fd5000000000000000000

1 output(s) for total of 9.811712017000 dcy

stealth address amount amount idx
00: ac142a3d170a00a0dd2906ae002578004eb7d3cee5b4a1ef3ce522c4b44c16c7 9.811712017000 972635 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": 542126, "vin": [ { "gen": { "height": 542116 } } ], "vout": [ { "amount": 9811712017, "target": { "key": "ac142a3d170a00a0dd2906ae002578004eb7d3cee5b4a1ef3ce522c4b44c16c7" } } ], "extra": [ 1, 236, 233, 117, 132, 253, 130, 202, 8, 205, 195, 127, 70, 187, 67, 230, 86, 170, 140, 129, 180, 184, 223, 240, 120, 56, 216, 87, 199, 3, 137, 182, 42, 2, 17, 0, 0, 0, 23, 46, 107, 31, 213, 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