Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 287037a13cc960825e1cab9799c0bea4aa2f956a85e94d44f5e34127f18ab57e

Tx prefix hash: 223dcfd465422bf3d5a3af972c5d65f1aa7156e474275f10a4a8964fa7ed39ad
Tx public key: f209ef69a2e71fb493d43cdc6ec7138e5227fdde18f370649b00873caa5b4357
Timestamp: 1719896484 Timestamp [UCT]: 2024-07-02 05:01:24 Age [y:d:h:m:s]: 00:334:16:18:58
Block: 1056697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239187 RingCT/type: yes/0
Extra: 01f209ef69a2e71fb493d43cdc6ec7138e5227fdde18f370649b00873caa5b435702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4362bfe81b72e8389aa5ab8a53863a2bf382d3b3963ae545617592d29b2ad4b9 0.600000000000 1527114 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": 1056707, "vin": [ { "gen": { "height": 1056697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4362bfe81b72e8389aa5ab8a53863a2bf382d3b3963ae545617592d29b2ad4b9" } } ], "extra": [ 1, 242, 9, 239, 105, 162, 231, 31, 180, 147, 212, 60, 220, 110, 199, 19, 142, 82, 39, 253, 222, 24, 243, 112, 100, 155, 0, 135, 60, 170, 91, 67, 87, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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