Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9eda32896af7f66421c5f52f6d56d6d36ea12c49b6c07e7a02dc318d91c91233

Tx prefix hash: f945c78b13db2edfc0239f804f578b8a3df455c62e354a3c562bd229b5378e7b
Tx public key: 1c472171cd46bde1d32bfc0db0a59af187ed1ee8ff205668a4fbd94a7ce4a2ad
Timestamp: 1724927753 Timestamp [UCT]: 2024-08-29 10:35:53 Age [y:d:h:m:s]: 00:230:16:37:22
Block: 1098410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164738 RingCT/type: yes/0
Extra: 011c472171cd46bde1d32bfc0db0a59af187ed1ee8ff205668a4fbd94a7ce4a2ad02110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7343992f83c21484e3360e7fcf220f90dbc3d2c88525945f7902972f323320 0.600000000000 1574115 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": 1098420, "vin": [ { "gen": { "height": 1098410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7343992f83c21484e3360e7fcf220f90dbc3d2c88525945f7902972f323320" } } ], "extra": [ 1, 28, 71, 33, 113, 205, 70, 189, 225, 211, 43, 252, 13, 176, 165, 154, 241, 135, 237, 30, 232, 255, 32, 86, 104, 164, 251, 217, 74, 124, 228, 162, 173, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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