Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 203ba58401322c65cd5a43cdc3ecde6b1ab988fae6b64d8eb2180264679e4e67

Tx prefix hash: 88692db0340d16e963c3737bf89bb3b23e993c1735cf564f18391b5827f9d11b
Tx public key: 030afce019cbd1efb79a69c2cac34e0cfdcf03da84080ecf23f56c78d5ffc543
Timestamp: 1663898618 Timestamp [UCT]: 2022-09-23 02:03:38 Age [y:d:h:m:s]: 02:110:05:05:27
Block: 593776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600377 RingCT/type: yes/0
Extra: 01030afce019cbd1efb79a69c2cac34e0cfdcf03da84080ecf23f56c78d5ffc543021100000001faf35c9c000000000000000000

1 output(s) for total of 6.616287852000 dcy

stealth address amount amount idx
00: 1d3921a0f8a315a8ceffcb670f5a6d384e66961ddf7fbb0f4865af2dab2a1e98 6.616287852000 1028589 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": 593786, "vin": [ { "gen": { "height": 593776 } } ], "vout": [ { "amount": 6616287852, "target": { "key": "1d3921a0f8a315a8ceffcb670f5a6d384e66961ddf7fbb0f4865af2dab2a1e98" } } ], "extra": [ 1, 3, 10, 252, 224, 25, 203, 209, 239, 183, 154, 105, 194, 202, 195, 78, 12, 253, 207, 3, 218, 132, 8, 14, 207, 35, 245, 108, 120, 213, 255, 197, 67, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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