Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4797932c6dc657e50b922b55e37868aff767d1d475011ad2839b588547f36ae2

Tx prefix hash: 74ce81364fc46dfb30eaec39b37deebbd82b1424d189098b7d8cb86a05a37528
Tx public key: c9e7dc8bd991d7c5c4baa9bd3c544abd1a1b2a7c51baa382e0023a640ded4566
Timestamp: 1643953653 Timestamp [UCT]: 2022-02-04 05:47:33 Age [y:d:h:m:s]: 03:005:20:39:35
Block: 431837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 783374 RingCT/type: yes/0
Extra: 01c9e7dc8bd991d7c5c4baa9bd3c544abd1a1b2a7c51baa382e0023a640ded4566021100000014a8c141c5000000000000000000

1 output(s) for total of 22.758974714000 dcy

stealth address amount amount idx
00: 3ea61cd724eefc92adadc55b1a1a864e760de8dc4023159d3af36ca6f19b356f 22.758974714000 842180 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": 431847, "vin": [ { "gen": { "height": 431837 } } ], "vout": [ { "amount": 22758974714, "target": { "key": "3ea61cd724eefc92adadc55b1a1a864e760de8dc4023159d3af36ca6f19b356f" } } ], "extra": [ 1, 201, 231, 220, 139, 217, 145, 215, 197, 196, 186, 169, 189, 60, 84, 74, 189, 26, 27, 42, 124, 81, 186, 163, 130, 224, 2, 58, 100, 13, 237, 69, 102, 2, 17, 0, 0, 0, 20, 168, 193, 65, 197, 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