Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c81bf383063c3b89e20a40f6f846ba20f58f5942da1cf9938f278fe2cef15ae2

Tx prefix hash: f3da5390f62ae028c145cd1f44d62d4a9192e2d4458143a5c2cd37d427d049c0
Tx public key: d8dea096125407e622e9a809f442e548b1f43d76226d2d6c283bc3e4c9f87874
Timestamp: 1677763167 Timestamp [UCT]: 2023-03-02 13:19:27 Age [y:d:h:m:s]: 02:250:14:54:50
Block: 708275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 698402 RingCT/type: yes/0
Extra: 01d8dea096125407e622e9a809f442e548b1f43d76226d2d6c283bc3e4c9f878740211000000015029cbac000000000000000000

1 output(s) for total of 2.761790982000 dcy

stealth address amount amount idx
00: f37deb9eab5e4b6d59644f90e7667d6fb76caf08b3e2d665d668044f2a5752bc 2.761790982000 1152130 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": 708285, "vin": [ { "gen": { "height": 708275 } } ], "vout": [ { "amount": 2761790982, "target": { "key": "f37deb9eab5e4b6d59644f90e7667d6fb76caf08b3e2d665d668044f2a5752bc" } } ], "extra": [ 1, 216, 222, 160, 150, 18, 84, 7, 230, 34, 233, 168, 9, 244, 66, 229, 72, 177, 244, 61, 118, 34, 109, 45, 108, 40, 59, 195, 228, 201, 248, 120, 116, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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