Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00041ce8839a12a09a36aebfb6ed5d180df29b6e4225ce51cf9d57b90ae12dfc

Tx prefix hash: 69194adfc5b0a02ce3e2c6d0fe0bceacb12b5705ab1a4497732c662194201e7c
Tx public key: 775aa8fa2fe4f126bdb2637476159c968f70411ca631e6e4579e3c27ed0121bf
Timestamp: 1721638358 Timestamp [UCT]: 2024-07-22 08:52:38 Age [y:d:h:m:s]: 00:282:00:09:14
Block: 1071130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201516 RingCT/type: yes/0
Extra: 01775aa8fa2fe4f126bdb2637476159c968f70411ca631e6e4579e3c27ed0121bf0211000000020cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aacc4c5c3439e0581c964ce42a61c11e6ee1f3df350c645c4e50480df6e9348 0.600000000000 1543241 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": 1071140, "vin": [ { "gen": { "height": 1071130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aacc4c5c3439e0581c964ce42a61c11e6ee1f3df350c645c4e50480df6e9348" } } ], "extra": [ 1, 119, 90, 168, 250, 47, 228, 241, 38, 189, 178, 99, 116, 118, 21, 156, 150, 143, 112, 65, 28, 166, 49, 230, 228, 87, 158, 60, 39, 237, 1, 33, 191, 2, 17, 0, 0, 0, 2, 12, 206, 6, 54, 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