Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c20e291d4c159fda6500dafa43bcc0232eaaf055d597c00466640c5e30476c6

Tx prefix hash: 67fdbc3cf33d21c98153ce657ca53d1cf8c48f435e198ab4bd890d0ce5ed44c6
Tx public key: 3b41c1817278a4c17e2aa0025ea1f7010637d277d123c91d5c80ee95f82d300c
Timestamp: 1728401283 Timestamp [UCT]: 2024-10-08 15:28:03 Age [y:d:h:m:s]: 00:182:03:01:56
Block: 1127211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129947 RingCT/type: yes/0
Extra: 013b41c1817278a4c17e2aa0025ea1f7010637d277d123c91d5c80ee95f82d300c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c04c8103840eb3e872956c1e3c0d3a6f85403c32b59b150141c055f0130b092f 0.600000000000 1610012 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": 1127221, "vin": [ { "gen": { "height": 1127211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c04c8103840eb3e872956c1e3c0d3a6f85403c32b59b150141c055f0130b092f" } } ], "extra": [ 1, 59, 65, 193, 129, 114, 120, 164, 193, 126, 42, 160, 2, 94, 161, 247, 1, 6, 55, 210, 119, 209, 35, 201, 29, 92, 128, 238, 149, 248, 45, 48, 12, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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