Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7525e637be6fc457a8d48d5bfea48b64f62799315a368ce442e024478b3d569c

Tx prefix hash: 5cb27894fd39409815302d9e56711a7ace361fc6177d54b7180c87dbab838ef9
Tx public key: 753acec7b4cc6a8febc424b254763d3b4409c4f8e72dee33f5166b096aa0ad8d
Timestamp: 1723169139 Timestamp [UCT]: 2024-08-09 02:05:39 Age [y:d:h:m:s]: 00:281:08:38:52
Block: 1083819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201016 RingCT/type: yes/0
Extra: 01753acec7b4cc6a8febc424b254763d3b4409c4f8e72dee33f5166b096aa0ad8d02110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 851cfb55c225e8446739abf1677fec7afa5a3a804f0c54ad769058e582b3d482 0.600000000000 1557878 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": 1083829, "vin": [ { "gen": { "height": 1083819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "851cfb55c225e8446739abf1677fec7afa5a3a804f0c54ad769058e582b3d482" } } ], "extra": [ 1, 117, 58, 206, 199, 180, 204, 106, 143, 235, 196, 36, 178, 84, 118, 61, 59, 68, 9, 196, 248, 231, 45, 238, 51, 245, 22, 107, 9, 106, 160, 173, 141, 2, 17, 0, 0, 0, 14, 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