Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03b44671a42c5081f5734e35aa64b3e27b6b187fe94f5f257550862d2dbc6188

Tx prefix hash: 47314ec3ca2df1b91908487344730cd0e3c21d35660f2d4a3fd9ad888ef6fe1c
Tx public key: e12ff781496ebfd27e9a3d6b0a0c946220a807d272cfec8db465a3cf05a2261e
Timestamp: 1695786845 Timestamp [UCT]: 2023-09-27 03:54:05 Age [y:d:h:m:s]: 01:203:07:49:00
Block: 857007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406390 RingCT/type: yes/0
Extra: 01e12ff781496ebfd27e9a3d6b0a0c946220a807d272cfec8db465a3cf05a2261e0211000000074b8f5122000000000000000000

1 output(s) for total of 0.887932791000 dcy

stealth address amount amount idx
00: 6bfb64a0a4cbed471dd910f0ccd6a4fb41062b56f45cbe4f1940b089a34c659f 0.887932791000 1311107 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": 857017, "vin": [ { "gen": { "height": 857007 } } ], "vout": [ { "amount": 887932791, "target": { "key": "6bfb64a0a4cbed471dd910f0ccd6a4fb41062b56f45cbe4f1940b089a34c659f" } } ], "extra": [ 1, 225, 47, 247, 129, 73, 110, 191, 210, 126, 154, 61, 107, 10, 12, 148, 98, 32, 168, 7, 210, 114, 207, 236, 141, 180, 101, 163, 207, 5, 162, 38, 30, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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