Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90a438a30c9e97435bc83f3ad7b588f8e1a292472e1bad5ddd1275cb1abe5fda

Tx prefix hash: 7d1f700adbe6555ba3417717d21d21ce693b1f51c006d0ab827ff63c65a28b73
Tx public key: 30631f9ecb870c51f2f7604e1dee24090999c40ef693e2dced8c84ade1e30c31
Timestamp: 1703063263 Timestamp [UCT]: 2023-12-20 09:07:43 Age [y:d:h:m:s]: 02:003:04:45:18
Block: 917143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522047 RingCT/type: yes/0
Extra: 0130631f9ecb870c51f2f7604e1dee24090999c40ef693e2dced8c84ade1e30c31021100000003e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69a3c3b41b505d0c50c9d4f7226031f434673d0bab08783a8c07ad5e3c6a3984 0.600000000000 1374711 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": 917153, "vin": [ { "gen": { "height": 917143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69a3c3b41b505d0c50c9d4f7226031f434673d0bab08783a8c07ad5e3c6a3984" } } ], "extra": [ 1, 48, 99, 31, 158, 203, 135, 12, 81, 242, 247, 96, 78, 29, 238, 36, 9, 9, 153, 196, 14, 246, 147, 226, 220, 237, 140, 132, 173, 225, 227, 12, 49, 2, 17, 0, 0, 0, 3, 228, 187, 107, 131, 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