Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53dd873d8174419fa9b6c016543de7d8a9653e8a57c03bef7484c667c277a3d9

Tx prefix hash: 0080c5198759e5832988e7e6cdf364b087694e375c8d5ff589aa3d03a4a9a967
Tx public key: 977118dff67c28243e840aaa1b7797a1e3ca6865abc4220c8cb7e60d13789e0e
Timestamp: 1730305298 Timestamp [UCT]: 2024-10-30 16:21:38 Age [y:d:h:m:s]: 00:158:14:43:56
Block: 1142922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113182 RingCT/type: yes/0
Extra: 01977118dff67c28243e840aaa1b7797a1e3ca6865abc4220c8cb7e60d13789e0e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f0867adda7efe2300841e7d770c2216db7490c59e52578ebcac5bd1f1d9c89f 0.600000000000 1626779 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": 1142932, "vin": [ { "gen": { "height": 1142922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f0867adda7efe2300841e7d770c2216db7490c59e52578ebcac5bd1f1d9c89f" } } ], "extra": [ 1, 151, 113, 24, 223, 246, 124, 40, 36, 62, 132, 10, 170, 27, 119, 151, 161, 227, 202, 104, 101, 171, 196, 34, 12, 140, 183, 230, 13, 19, 120, 158, 14, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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