Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8fc057bfe75648a36f304d7a0e6f0e29eea0b6afba0acc6a23139acdd01d221

Tx prefix hash: bb535077646ccbe9e7a990dc9e30bace93ef71952925af1a04d9b29ef65a71e0
Tx public key: a2bdf4776deea1e6899005551199ff5a2eda3c1242298522038c29ae51a46ebc
Timestamp: 1696954095 Timestamp [UCT]: 2023-10-10 16:08:15 Age [y:d:h:m:s]: 01:251:03:26:15
Block: 866707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440444 RingCT/type: yes/0
Extra: 01a2bdf4776deea1e6899005551199ff5a2eda3c1242298522038c29ae51a46ebc02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.824593589000 dcy

stealth address amount amount idx
00: 785f152b7e5bdc8df05e460feca2cdece3f6e9f0fe2eaab3f973ee70f27ba917 0.824593589000 1321331 of 0

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": 866717, "vin": [ { "gen": { "height": 866707 } } ], "vout": [ { "amount": 824593589, "target": { "key": "785f152b7e5bdc8df05e460feca2cdece3f6e9f0fe2eaab3f973ee70f27ba917" } } ], "extra": [ 1, 162, 189, 244, 119, 109, 238, 161, 230, 137, 144, 5, 85, 17, 153, 255, 90, 46, 218, 60, 18, 66, 41, 133, 34, 3, 140, 41, 174, 81, 164, 110, 188, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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