Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6d23d6586786d8c9f1ffc8f039b8af25a84282024402cf7328e72bf32f4b5f6

Tx prefix hash: 96affe898e233de04e73809167f49d40a69d3d17f17189c3164fcbedd64e3c0a
Tx public key: 2c4d28e35296ca477f025d9a4223665c92783152450a5dcca0e8becca413d77a
Timestamp: 1682287615 Timestamp [UCT]: 2023-04-23 22:06:55 Age [y:d:h:m:s]: 01:355:00:38:08
Block: 745148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515000 RingCT/type: yes/0
Extra: 012c4d28e35296ca477f025d9a4223665c92783152450a5dcca0e8becca413d77a021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.084565571000 dcy

stealth address amount amount idx
00: 32b52768dd430b2f4bd9de3ca8bb9af3e532a3cd76e6d116fa5f0a8d1dc6cb41 2.084565571000 1192573 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": 745158, "vin": [ { "gen": { "height": 745148 } } ], "vout": [ { "amount": 2084565571, "target": { "key": "32b52768dd430b2f4bd9de3ca8bb9af3e532a3cd76e6d116fa5f0a8d1dc6cb41" } } ], "extra": [ 1, 44, 77, 40, 227, 82, 150, 202, 71, 127, 2, 93, 154, 66, 35, 102, 92, 146, 120, 49, 82, 69, 10, 93, 204, 160, 232, 190, 204, 164, 19, 215, 122, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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